home *** CD-ROM | disk | FTP | other *** search
/ ftp.cs.arizona.edu / ftp.cs.arizona.edu.tar / ftp.cs.arizona.edu / icon / newsgrp / group98b.txt / 000043_icon-group-sender _Wed May 27 08:21:22 1998.msg < prev    next >
Internet Message Format  |  2000-09-20  |  2KB
  1. Return-Path: <icon-group-sender>
  2. Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
  3.     by baskerville.CS.Arizona.EDU (8.8.8/8.8.7) with SMTP id IAA03054
  4.     for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Wed, 27 May 1998 08:21:21 -0700 (MST)
  5. Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
  6.     id AA29918; Wed, 27 May 1998 08:21:15 -0700
  7. From: Otfried Geffert <og@stardivision.de>
  8. Date: Wed, 27 May 1998 11:37:39 GMT
  9. Message-Id: <19980527.11373903@og-1042.stardiv.de>
  10. Subject: Re: Writing compilers in Icon
  11. To: Guy Laden <guy@math.tau.ac.il>
  12. Cc: icon-group@baskerville.CS.Arizona.EDU
  13. In-Reply-To: <199805222014.XAA02171@orion.math.tau.ac.il>
  14. References: <199805222014.XAA02171@orion.math.tau.ac.il>
  15. X-Mailer: Mozilla/3.0 (compatible; StarOffice/4.0; WinNT/Win95)
  16. X-Priority: 3 (Normal)
  17. Mime-Version: 1.0
  18. Content-Type: text/plain; charset=ISO-8859-1
  19. Content-Transfer-Encoding: quoted-printable
  20. Errors-To: icon-group-errors@optima.CS.Arizona.EDU
  21. Status: RO
  22. Content-Length: 1125
  23.  
  24. Hi Guy,
  25.  
  26. in 'The Icon programming language' 3rd edition from Griswold &=20
  27. Griswold
  28. they describe how to use Icon for syntax analysis using
  29.  
  30. - alternation
  31. - recursive lists=20
  32. - generators to represent syntactical constructs
  33.  
  34. on page 220-226.
  35.  
  36. It's really worth reading.=20
  37.  
  38. I myself wrote a compiler/linker, but I used lex/yacc and C, because
  39. I did'nt know Icon in those days. With Icon I would have implemented=20=
  40.  
  41. it much faster, especially because of the builtin data
  42. structures.
  43.  
  44. Regards, Otfried
  45.  
  46.  
  47. >>>>>>>>>>>>>>>>>>  <<<<<<<<<<<<<<<<<<
  48.  
  49. Guy Laden <guy@math.tau.ac.il> wrote:
  50.  
  51.  
  52. > I noticed the newly announced implementation of Jcon is written in=20=
  53.  
  54. Icon.=20
  55. > I was wondering whether anybody can comment on how suitable they=20
  56. > find Icon for writing compilers? Do any of Icon's unique features
  57. > prove especially useful for this task? I'm wondering more about
  58. > generators and goal-directed evaluation; the built-in data-structures =
  59.  
  60. > are obviously useful.
  61. >=20
  62. > btw, does anybody have an Icon grammar they are willing to share
  63. > that is suitable for recursive descent parsing?
  64. >=20
  65. > Regards,
  66. > Guy.
  67. >=20
  68.  
  69.  
  70.  
  71.